Add policy container to request #1231
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced May 6, 2021
antosart
commented
May 6, 2021
annevk
reviewed
May 6, 2021
annevk
reviewed
May 6, 2021
… the conditional on each redirect)
|
@antosart I moved the defaulting slightly and also did some more rewrapping. Let me know if you have any final thoughts. I'll reference w3c/webappsec-csp#494 from the eventual commit message. I suppose this should land first? |
|
@annevk thanks! Yes, this one should land first, since w3c/webappsec-csp#494 depends on this one. |
antosart
added a commit
to w3c/webappsec-csp
that referenced
this pull request
May 12, 2021
This change depends on whatwg/fetch#1231 and whatwg/html#6659 which add and populate a request's policy container. This change relies on the request's policy container CSP list (instead of the request's client's environment setting object's CSP list) for the checks. This enforces consistency, since the the request's client's environment setting object's CSP list can change during the lifetime of an asynchronous fetch (for example, when following redirects, or when doing a response check), while the request's policy container CSP list is a snapshot at request's creation time.
ryandel8834
added a commit
to ryandel8834/WebAppSec-CSP
that referenced
this pull request
Aug 13, 2022
This change depends on whatwg/fetch#1231 and whatwg/html#6659 which add and populate a request's policy container. This change relies on the request's policy container CSP list (instead of the request's client's environment setting object's CSP list) for the checks. This enforces consistency, since the the request's client's environment setting object's CSP list can change during the lifetime of an asynchronous fetch (for example, when following redirects, or when doing a response check), while the request's policy container CSP list is a snapshot at request's creation time.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds a policy container to the request. The idea is to snapshot the policies when the request is created and have them available for the whole lifetime of the fetch algorithm. Together with a change to CSP, this will solve #832.
Preview | Diff